Methods and systems for imaging device form field management

ABSTRACT

Aspects of the present invention relate to systems, methods and devices for modifying and managing form documents with an application that receives input from an imaging device user interface and from other sources. Some aspects relate to a input field definition file that is transmitted to the imaging device and which comprises display parameters and UI options for prompting a user for field input and as well as instructions for obtaining field data from other sources.

RELATED REFERENCES

This application is a continuation of U.S. patent application Ser. No.11/256,493, entitled “Methods and Systems for Imaging Device DocumentModification,” filed on Oct. 21, 2005 which is a continuation-in-partof:

U.S. patent application Ser. No. 11/192,615, entitled “Methods andSystems for Providing Remote File Structure Access on an ImagingDevice,” filed on Jul. 29, 2005;

U.S. patent application Ser. No. 11/233,270, entitled “Methods andSystems for Imaging Device Display Standardization,” filed on Sep. 22,2005;

U.S. patent application Ser. No. 10/962,248, entitled “Methods andSystems for Imaging Device Remote Application Interaction,” filed onOct. 8, 2004;

U.S. patent application Ser. No. 10/961,793, entitled “Methods andSystems for Imaging Device Remote Form Management,” filed on Oct. 8,2004;

U.S. patent application Ser. No. 10/961,911, entitled “Methods andSystems for Imaging Device Remote Location Functions,” filed on Oct. 8,2004;

U.S. patent application Ser. No. 10/961,594, entitled “Methods andSystems for Imaging Device Remote document Management,” filed on Oct. 8,2004; and

U.S. patent application Ser. No. 10/962,103, entitled “Methods andSystems for Imaging Device Document Translation,” filed on Oct. 8, 2004;

and which claims the benefit of U.S. Provisional Patent Application No.60/704,066, entitled “Methods and Systems for Imaging DeviceApplications,” filed Jul. 28, 2005.

BACKGROUND OF THE INVENTION

Imaging devices such as printers, copiers, scanners and fax machines canhave a wide array of functions and capabilities to fit specific uses orcombinations of uses. Imaging devices often take the form of amulti-function peripheral device (MFP) that combines the functions oftwo or more of the traditionally separated imaging devices. An MFP maycombine any number of imaging devices, but typically comprises thefunctions of a printer, scanner, copier and fax machine.

Some imaging devices may contain computing resources for data storageand processing such as processors, hard disk drives, memory and otherdevices. As imaging devices add more features and functions, they becomemore costly and complex.

More complex imaging devices and MFPs may comprise network connectivityto provide communication with other computing devices, such as personalcomputers, other imaging devices, network servers and other apparatus.This connectivity allows the imaging device to utilize off-boardresources that are available on a connected network.

Imaging devices typically have a user input panel with an array ofbuttons, knobs and other user input devices. Some devices also have adisplay panel, which can be for display only or can be a touch paneldisplay that enables user input directly on the display.

Devices with touch panel displays or displays with buttons arranged incooperation with the display can display menu data that may be selectedby user input. This menu data is typically driven by an on-board servermodule within the imaging device.

BRIEF SUMMARY OF THE INVENTION

Embodiments of the present invention comprise systems, methods anddevices for interacting with a remote computing device from an imagingdevice. These embodiments comprise remote computing devices configuredto communicate with imaging devices, imaging devices configured tocommunicate with remote computing devices and systems comprising variouscombinations of remote computing devices in communication with imagingdevices.

Embodiments of the present invention comprise systems and methods formodifying documents with an imaging device. Some of these methodscomprise the entry of document field data through an imaging device userinterface. Some of these methods comprise automated entry of documentfield data.

The foregoing and other objectives, features, and advantages of theinvention will be more readily understood upon consideration of thefollowing detailed description of the invention taken in conjunctionwith the accompanying drawings.

BRIEF DESCRIPTION OF THE SEVERAL DRAWINGS

FIG. 1 is a diagram of an embodiment of the present invention comprisingan imaging device in connection with a remote computing device;

FIG. 2 is an image of an exemplary user interface for an imaging device;

FIG. 3 shows an exemplary imaging device;

FIG. 4 is a chart depicting steps of an imaging device method;

FIG. 5 is a chart depicting steps of an imaging device method using amarkup language;

FIG. 6 shows an exemplary remote computing device embodiment;

FIG. 7 is a diagram showing components of an exemplary remote computingdevice;

FIG. 8 is a chart showing steps of a remote computing device method;

FIG. 9 is a chart showing steps of a remote computing device methodusing a markup language;

FIG. 10 is a diagram showing a system comprising multiple imagingdevices in connection with a remote computing device;

FIG. 11 is a chart showing steps of a method that may be employed by thesystem depicted in FIG. 10.

FIG. 12 is a diagram showing elements of a system embodiment of thepresent invention;

FIG. 13 is a chart showing the steps of an exemplary documentmodification method;

FIG. 14 is a chart showing the steps of an exemplary documentmodification method using user characteristic data;

FIG. 15 is a chart showing the steps of an exemplary documentmodification method comprising user characteristic input and documentselection;

FIG. 16 is a chart showing the steps of an exemplary documentmodification method wherein supplemental user data is retrieved;

FIG. 17 is a chart showing the steps of an exemplary documentmodification method comprising a user query;

FIG. 18 is a chart showing the steps of an exemplary documentmodification method comprising document display on an imaging device;

FIG. 19 is a chart showing the steps of an exemplary documentmodification method using XML and SOAP;

FIG. 20 is a chart showing the steps of an exemplary documentmodification method comprising remote menu data;

FIG. 21 is a chart showing the steps of an exemplary documentmodification method executed by an imaging device;

FIG. 22 is a chart showing the steps of an exemplary documentmodification method executed by a remote computing device;

FIG. 23 is a chart showing the steps of an exemplary documentmodification method executed by an imaging device wherein remote data isaccessed;

FIG. 24 is a chart showing the steps of an exemplary documentmodification method executed by a remote computing device wherein remotedate is accessed;

FIG. 25 is a chart showing the steps of an exemplary documentmodification method comprising remote menu data and remote documentmodification;

FIG. 26 is a chart showing the steps of an exemplary documentmodification method comprising document content modification on animaging device with output to a destination;

FIG. 27 is a chart showing the steps of an exemplary documentmodification method comprising document content modification on animaging device with document output through an imaging device function;

FIG. 28 is a chart showing the steps of an exemplary documentmodification method comprising document content modification on animaging device with remote document storage;

FIG. 29 is a chart showing an exemplary form fill application;

FIG. 30 is a chart showing an exemplary form request procedure;

FIG. 31 is a chart showing an exemplary form fill procedure;

FIG. 32 is a chart showing the steps of an exemplary form fill methodwith IDev UI interaction; and

FIG. 33 is a chart showing the steps of an exemplary form fill methodcomprising IDev UI interaction and appending form file field data.

DETAILED DESCRIPTION

Embodiments of the present invention will be best understood byreference to the drawings, wherein like parts are designated by likenumerals throughout. The figures listed above are expressly incorporatedas part of this detailed description.

It will be readily understood that the components of the presentinvention, as generally described and illustrated in the figures herein,could be arranged and designed in a wide variety of differentconfigurations. Thus, the following more detailed description of theembodiments of the methods and systems of the present invention is notintended to limit the scope of the invention but it is merelyrepresentative of the presently preferred embodiments of the invention.

Elements of embodiments of the present invention may be embodied inhardware, firmware and/or software. While exemplary embodiments revealedherein may only describe one of these forms, it is to be understood thatone skilled in the art would be able to effectuate these elements in anyof these forms while resting within the scope of the present invention.

Embodiments of the present invention comprise interfaces andarchitecture that integrate imaging devices with remote computing deviceapplications and environments to provide solutions that may not bepossible solely with an imaging device alone. Some embodiments comprisean infrastructure and set of interfaces that allow applications on anetwork to programmatically control imaging device functions andinteract with a user through an imaging device input panel. Softwarefunctions that are not practical within the imaging device can beperformed on the server but are accessible from the imaging device.

For the purposes of this specification and claims, an imaging device(IDev) may be described as a device that performs an imaging function.Imaging functions comprise scanning, printing, copying, imagetransmission (sending and receiving), image conversion and otherfunctions. Exemplary imaging devices comprise printers, copiers,facsimile machines, scanners, computing devices that transmit, convertor process images and other devices. An IDev may also perform multipleimaging functions. For example, and not by way of limitation, amulti-function peripheral device (MFP), which typically has thecapability to perform a plurality of functions comprising a printer,scanner, copier and/or a facsimile machine or imagetransmitter/receiver, is a type of imaging device. Other MFP imagingdevices may comprise other combinations of functions and still qualifyas an IDev.

For the purposes of this specification and claims, a remote computingdevice (RCD) is a device capable of processing data and communicatingwith other devices through a communications link. An RCD is a remotedevice because it requires a communications link, such as a networkconnection, a telephone line, a serial cable or some other wired orwireless link to communicate with other devices such as an imagingdevice. Some exemplary RCDs are network servers, networked computers andother processing and storage devices that have communications links.

Some embodiments of the present invention may be described withreference to FIGS. 1 & 2. These embodiments comprise an imaging device(IDev) 4 that may be a multi-function peripheral device (MFP) or asingle function device. The imaging device 4 further comprises a userinterface (UI) panel 2, which may comprise input buttons 14 and adisplay device or may comprise a touch panel system with or withoutbuttons 14. User input and display may also be performed through aseparate UI device 8, which may be connected to the imaging device 4 bya communication link 12, such as a USB connection, a network cable, awireless connection or some other communications link. UI device 8 maycomprise an input device, such as a keyboard or buttons as well as adisplay device, which may also be a touch screen panel. UI device 8 mayalso comprise an interface for transfer of instructions that are inputto the device 8 from a remote input device. This form of UI device 8 maycomprise memory sticks, USB memory cards and other storage devices thatmay be configured to store input for transfer to an imaging device.

These embodiments further comprise a remote computing device (RCD) 6that is linked to the imaging device 4 via a communications link 10,such as a network connection. This network connection may be a typicalwired connection or a wireless link.

Embodiments of the present invention may provide menu data from the RCD6 to the imaging device UI panel 2 or remote panel 8 via the networkconnection 10. Once this menu data is fed to the imaging device 4, an UIpanel 2, 8 on the imaging device 4 may be used to interact withapplications that run on the remote computing device 6. User inputreceived from UI panels 2, 8 may be returned directly to the remotecomputing device 6.

A Web Service is a software application identified by a Uniform ResourceIdentifier (URI), whose interfaces and binding are capable of beingdefined, described and discovered by Extensible Markup Language (XML)artifacts and supports direct interactions with other softwareapplications using XML based messages via Internet-based protocols.

An application on the remote computing device 6 may use one or more WebServices to control various features in the imaging device 4, such asenabling, disabling or setting device values or controlling devicefunctions.

Embodiments of the present invention allow network applications runningon remote computing devices to interact with the user of the imagingdevice through the imaging device I/O panel. These embodiments allowimaging device user interface (UI) control (i.e., touch panel,button/display) by applications. Some embodiments may also integratecustom display screens or menus with the native imaging device UI.Embodiments may hand off control of imaging device functions betweenstandard operation modes performed on the imaging device in response touser input to an imaging device UI and open systems modes that utilizenetwork resources, such as applications on RCDs, through user input atthe imaging device UI.

Embodiments of the present invention comprise network-based applicationsthat have full control over the imaging device UI to display text andgraphics in any format. In these embodiments, the application canprogrammatically display buttons, textboxes, graphics, etc. in anylayout desired.

In some embodiments, the UI layout is easy to program using a standardlanguage, such as a markup language. These languages comprise HypertextMarkup Language (HTML), Extensible Markup Language (XML), WirelessMarkup Language (WML), Extensible Hypertext Markup Language (XHTML) andother languages.

In some embodiments of the present invention a remote computing deviceapplication or server application is able to request a keyboard UI to bedisplayed on the imaging device display 12, 8. In some embodiments, thisfunctionality is available on the imaging device and does not need to berecreated by remote computing device applications. In some embodiments,the remote computing device may define the keyboard prompt and defaultvalues. These embodiments may comprise a remote computing device that isable to rename imaging device UI buttons, such as the OK and Cancelbuttons as well as define additional buttons.

In some embodiments, menu templates may be served to the imaging deviceUI by the imaging device itself 4 or from a remote computing device 6.

External Authorization Application

Some embodiments of the present invention may comprise a remotecomputing device application that is registered as the ExternalAuthorization server. The External Authorization application may controlaccess to the imaging device and may have top-level control of the UI.UI control may be given to this application in the same manner thatcontrol is given to an internal auditor.

In these embodiments, when an imaging device system boots, it checks tosee if an External Authorization application is registered. If so, theimaging device is placed in disabled mode and the application iscontacted to take control of the UI. If the External Authorizationserver is not available, an error message may be displayed and thedevice may remain disabled. The imaging device may periodically try tocontact the External Authorization server until it is available. Table 1below describes what entity has control of the UI, in an exemplaryembodiment, when the device is in a disabled state.

TABLE 1 UI Control in Disabled State Indicator Button Press UI ControlLights Device boots External Application None Document Filing ExternalApplication None Image Send External Application None Copy ExternalApplication None Job Status Device - standard Job Status screens JobStatus Custom Settings Device - standard Custom Settings N/A screens OSMode Not available when device is disabledRemote Computing Device Applications

In embodiments of the present invention, access to the custom UI panelsof imaging devices may vary from application to application. Somesolutions, such as Document Management integration, may wish to leveragethe native Image Send screens, but display some custom UI's to gatheradditional information about a scan job. Other solutions, like customprinting applications, may be accessed from a separate mode than thenative functions.

In order to accommodate the diversified needs of these solutionsapplications, embodiments may support multiple integration points for UIcontrol. These integration points are based on a user action (“trigger”)for which applications may register. In some embodiments, applicationsmay be registered with target devices so that the device knows that when“trigger A” occurs on the front panel to contact “remote computingdevice B” for instructions. In exemplary embodiments, applications maybe integrated with an imaging device at any of several “trigger” points.

Remote computing devices may be registered to a specific function andcontacted when that function's hardware key is pressed (e.g. Image Send)on the imaging device UI. Any UI information provided by the remotecomputing device may be displayed instead of the standard functionscreens native to the imaging device. This trigger may be used forapplications that wish to replace the existing functions with completelycustom UI's, such as an alternative scan solution or a specializeddisplay, such as a “Section 508” compatible screen or otherspecialized-need interface that may have large buttons or otheraccommodations.

In some embodiments, each function on the imaging device may have a menuon the touch screen that remote computing devices, such as servers, canregister. This enables solutions applications to provide custom contentand still use some of the standard functionality provided by the imagingdevice. When a button assigned to a custom application is selected, amenu will be displayed with the solutions registered to that function.Users may select the desired solution and the remote computing devicewill be contacted for instructions.

In some embodiments, a stand-alone RCD mode that provides remotecomputing device application access can be accessed from the job queueportion of the UI that is displayed on every screen. This trigger pointmay be used for applications that do not fit within one of the standarddevice functions, such as custom printing solutions on an imagingdevice. When the RCD menu is selected, a menu will be displayed with thesolutions applications registered to the generic RCD mode. Users willselect the desired solution and the remote computing device will becontacted for instructions.

Hardware Key Interaction

In some embodiments of the present invention, when an imaging device isenabled, additional hardware keys may be used to manage the device.Hardware key assignments for an exemplary embodiment are shown in table2.

TABLE 2 Exemplary Hardware Key Assignments Button Press Standard IDevMode RCD Mode Mode keys (Copy, Clear current job settings, move to Clearcurrent job settings, Doc Filing, Image target screen move to targetscreen Send) and Custom Settings key Job Status key Move to Job Status,maintain Move to Job Status, current settings & UI location maintaincurrent settings & UI location Clear (C) Clears settings Sends clearevent to external application Clear All (CA) Clears settings, cancelsjob, and Cancels job and returns to returns to default IDev screendefault IDev screen (notification sent to external application) **WhenExternal Authorization is controlling the UI, only notification is sentStart Initiates scan function Initiates scan function Number keys Inputfor copy count or fax Not used numbers * Logs user out (disable deviceLogs user out (disable and contact External device and contact ExternalAuthorization for screens) Authorization for screens)

In some embodiments, in addition to the * key for logout, a timeoutperiod may be implemented. Some embodiments also comprise an auto clearsetting that can be configured for a given period of time, such as 10 to240 seconds (or disabled). In these embodiments, when there is noactivity for the time configured in auto clear, the device mayautomatically return to disabled mode and attempt to contact a remotecomputing device to retake control of the UI.

Error & Jam Notifications

Depending on a particular solution, a remote computing deviceapplication may have full or only partial control of the imaging deviceUI and a particular imaging job. In some embodiments, partial controlmay include cases where a remote computing device is monitoring clicks,but native modes are responsible for the UI interaction and controllingthe job. Partial control may also include cases where the remotecomputing device application is integrated with a native mode (UItrigger=function custom menu). In these embodiments, the imaging devicemay handle all error and jam notifications with only a notification sentto the relevant remote computing device application.

For some embodiments, in cases where the remote computing deviceapplication has full control over the UI and the job, error and jamnotifications may be handled differently depending on the type of error.For recoverable errors, a notification may be sent to the remotecomputing device application and the application may be responsible fordisplaying messages and resolving the error. For non-recoverable errors,the imaging device and RCD mode may interact to gracefully handle theerror condition (e.g. provide user with instructions for clearing jam).

Control Handoffs

In some embodiments, at different points throughout an imaging job,several applications may need control over an imaging device including,but not limited to, an External Authorization application, a standardRCD application, an imaging device native mode and other applications.The following section describes, for an exemplary embodiment, thevarious steps in an exemplary job, the entities that may have controlduring each step, and what type of control may be allowed.

Step 1: User provides credentials to access the device at the device UI.This step may be controlled by a remote computing device, such as anExternal Authorization application or by Internal Accounting (nativemode) in the imaging device itself. At the end of this step, the deviceis enabled. The External Authorization application may also specifydefault parameters or disable specific job parameters (e.g. default fileformat is PDF, but user may change; color mode is set to B/W and usermay not change).

Step 2: User sets parameters for the job using one of the native imagingdevice modes or a standard RCD application. At the end of this step theuser makes an input to initiate the job. When the input is made, anoptional notification may be sent to the standard RCD application, whichcan then change job parameters if desired. An e-mail application is oneexample of an application that may request notification when the userinput is made. A user may use native Image Send screens or other inputto select scan options and choose e-mail recipients. A user may thenselect a custom application button and choose the scan-to-e-mail optionfrom the menu. The e-mail application may then display custom screensfor the user to set permissions for the file. Once a user places theoriginal document(s) on the scanner and initiates the process, thee-mail application may capture the destination parameters set by theuser and change the target destination to the e-mail application FTPserver. The e-mail application may then receive the file, apply theappropriate permissions, and send to the e-mail recipients selected bythe user. A remote computing device application may also want to retakecontrol of the UI at this point, if, as in some embodiments, theapplication generates thumbnails of the scanned images and displays themto the user for verification.

Step 3: Once the job is initiated, the imaging device is responsible forscanning or RIPing the job and spooling it to the HDD. If the imagingdevice is configured to authorize jobs with an external authorizationapplication, it may send a click report to the application and wait forinstructions. The external authorization application may enable the jobfor sending/printing, cancel the job, or change job parameters (and thenenable). As an example, a rules-based printing application may wish tochange job parameters after it receives a click report. Some rules-basedprinting applications support rules-based printing and scanning that canlimit what each user is allowed to do based on the time of day, thedestination, or many other parameters. For example, only users in themarketing group may be able to scan high-quality color images. If a userfrom another group selects color and 600 dpi, a rules-based applicationmay change the parameters to color and 200 dpi. At the end of this stepthe job should either be authorized or canceled.

Step 4: In some embodiments, this may be an optional step, where thestandard RCD application in step 2 may have specified the destination asa HDD for temporary storage. This step may also be used, in someembodiments, by a Java application running on the imaging device. Forexample, a government office may have a custom encryption applicationrunning on the device that takes the scanned document, encrypts it, andthen requests the imaging device to send it to the target destinationselected by the user in step 2. In some embodiments, it may bebeneficial to send a notification to the external authorizationapplication after this step—because the imaging device does not know howlong the file will be on the HDD or what the application is going to dowith it—and after the send/print step.

Step 5: In the final step, the file is actually output. In typicalembodiments, the file is either sent over the network or printedlocally. At the end of this step, a notification that the job wassuccessfully completed should be sent to the external authorizationapplication and optionally, to the standard RCD application.

Device Control and Management API's

The API's may be used to allow a remote computing device application tocontrol access to an imaging device for vend applications and to managethe device from a remote location.

Device Control and Vend API

In some embodiments of the present invention, a Device Control and VendAPI allows applications to enable and disable access to the device andtrack click counts. The Device Control and Vend API may provide an RCDwith the following controls:

Enable/disable device of function—this may allow an RCD to enable ordisable access to the device as a whole or by function to enforceindividual user privileges. In some exemplary embodiments, the functionslisted in Table 3 may be selectively enabled or disabled by anapplication.

TABLE 3 Device Functions Enable/Disable Description Copy Copy function(Copy button) Image Send Scan and fax function, plus send from DocFiling (Image Send button) Document Filing All access to Document Filingfunctions (Document Filing button) Print Network prints, pull print fromfront panel, and print from Document Filing (No button control)

Report clicks used—at the end of a successful job, the clicks used maybe reported back to an RCD including:

TABLE 4 Job and Page Characteristics Fax PC- E-mail/ Scan Item CopyPrint Send Fax FTP Broadcast to HD JOB Characteristics Job Mode Yes YesYes Yes Yes Yes Yes Broadcast No No Yes Yes Yes Yes No Manage No. UserName Yes Yes Yes Yes Yes Yes Yes Address No No Yes Yes Yes # No StartTime Yes Yes Yes Yes Yes Yes Yes End Time Yes Yes Yes Yes Yes Yes YesTotal Page Yes Yes Yes Yes Yes Yes Yes Result Yes Yes Yes Yes Yes YesYes Error Cause No No Yes Yes Yes Yes No Doc Filing Yes Yes Yes Yes YesYes Yes Save Mode *1 *1 *1 *1 *1 *1 *1 File Name *1 Yes *1 Yes Yes *1Yes File Size Yes Yes *1 *1 *1 *1 Yes Resolution Yes Yes Yes Yes Yes YesYes Special Yes Yes Yes No Yes Yes Yes Finishing Yes Yes No No No No NoFile Format No No No No Yes Yes No Compression No No No No Yes Yes NoPAGE Characteristics Copy Yes Yes Yes Yes Yes # Yes Paper Size Yes YesYes Yes Yes Yes Yes Simplex/ Yes Yes Yes Yes Yes Yes Yes duplex PaperType Yes Yes Yes Yes No No Yes Page Yes Yes Yes Yes Yes Yes Yes *1 - Yeswhen Document Filing is used

Debit mode—in these embodiments, when an application enables the deviceit may specify if the current job requires authorization. If so, the jobwill be spooled to memory and click information (e.g., as defined inTable 4) will be sent to an RCD. An RCD will then notify the device ifthe job should be deleted or output/sent. At this point, the applicationalso has the option of changing job parameters. If the application doesnot require authorization, the job will continue as normal and a clickreport will be sent at the end of the job.

Print job accounting—in these embodiments, an RCD may wish to monitorprint jobs along with walk-up functions. For print job accounting, anIDev may monitor all incoming print jobs and send accounting data in thePJL header to an RCD for verification before printing the job. The RCDwill evaluate the accounting data (or lack thereof) and inform the IDevto continue with or cancel the job.

Report on unidentified jobs—in these embodiments, an RCD may also wishto monitor print jobs that it cannot associate to a specific user, suchas device reports and incoming fax jobs. The RCD can register to receiveclick counts for all unidentified jobs, so that it may bill them to ageneral account.

Device Management API

In some embodiments of the present invention, a Device Management APIallows a network application to remotely setup and manage the imagingdevice. In exemplary embodiments, the Device Management API may providean RCD with the following controls:

-   -   Device status—an RCD may request the current status of the        device. This is the same status information as reported on the        embedded web pages.    -   Device configuration—an RCD can retrieve a list of installed        options supported by the device.    -   Web Page settings—an RCD application can retrieve and set any of        the values that are configurable on the embedded web pages.    -   Key Operator Programs—an RCD application can retrieve and set        any of the values that are configurable in Key Operator        Programs, including software keys.    -   Custom Settings—an RCD application can retrieve and set any of        the values that are configurable in Custom Settings.    -   Job Status—an RCD application can retrieve the current job queue        and history information and reprioritize or delete jobs in the        queue.    -   Click counts—an RCD application can retrieve device total counts        and clicks for each function by account code.    -   Data Security settings—an RCD application may retrieve the        status information on the DSK (e.g. last erase) and initiate        data clear functions.    -   RED data—an RCD can retrieve all data typically sent in a RED        message.    -   Remote reboot—an RCD can initiate a reboot of the imaging        device.

The above groupings are provided only as an exemplary embodimentdetailing which settings should be included. In some embodiments, actualAPI's should be grouped by functional areas since there may be overlapbetween Key Operator settings and web page settings.

Internal Accounting API

In some embodiments, an Internal Accounting API may allow a remotecomputing device application to configure internal accounting and reportclick counts. In some exemplary embodiments an Internal Accounting APImay include:

-   -   Set Auditing Options—an RCD may set auditing options including        which modes auditing is enabled for, “account number security”,        and “cancel jobs of invalid accounts.”    -   Manage Account Codes—an RCD can add, edit, or delete account        codes    -   Account Limits—an RCD application can specify a maximum number        of clicks by function for individual account codes or for all        account codes    -   Account Reset—an RCD application can reset the click count for        an individual account or for all accounts    -   Retrieve Clicks—an RCD can retrieve the number of clicks by        function for each account code        Font and Form Management API

Some embodiments of the present invention may comprise a Font and FormManagement API, which allows an RCD application to remotely download andmanage fonts and forms in mass-storage. In some exemplary embodiments, aFont and Form Management API may provide a remote computing device withthe following controls:

-   -   Mass storage control—an RCD application can retrieve mass        storage status information including storage capacity, space        available, and write-protect mode plus modify write-protect        status.    -   Resource list—an RCD application can retrieve a list of stored        fonts and forms including font or macro ID, font number,        font/form name, escape sequence, and file size.    -   Download resource—an RCD application can download PCL fonts, PCL        macros, and PS fonts and forms. Any special processing that is        performed when a resource is downloaded via the web pages will        also be performed when the resource is downloaded via Open        Systems.    -   Delete resource—an RCD application can delete any resource        stored in mass storage.    -   Upload resources—an RCD application can upload an individual or        all resources. On devices where effective memory management is        unavailable, a server application can use this function to        “defrag” mass storage.    -   Font/macro ID's—an RCD application can assign or modify the ID's        assigned to PCL fonts and macros.        Firmware Management API

In some embodiments of the present invention, a Firmware Management APImay allow a remote computing device or network application to remotelydownload and manage the imaging device firmware. In some exemplaryembodiments, a Firmware Management API may provide a remote computingdevice (e.g., a server) with the following controls:

-   -   Firmware versions—an RCD application can retrieve the current        firmware version numbers.    -   Service mode—an RCD application can place the MFP in service        mode to lockout other jobs that will interfere with firmware        upgrade. Upon receiving a service mode request, the IDev will        stop accepting incoming jobs, complete all jobs in the queue,        and then notify the server that it is in service mode.    -   Update firmware—an RCD can download an updated firmware version        to the device. If a reboot is necessary, the IDev will perform        it automatically when download is complete.    -   Download status—the IDev will send a status notification        (success/error) to an RCD after firmware download.    -   Revert to previous version—if firmware update is not successful,        the application can request the IDev to revert to the previous        firmware version.

Device Function API's

In some embodiments of the present invention, device function API'sallow a remote computing device application to use existing imagingdevice functionality to provide new custom solutions.

Image Send API

In some embodiments, an Image Send API may provide the remote computingdevice application with the following controls:

-   -   Image Send Parameters—a remote computing device application can        get and set values for the following scan and fax parameters:        -   COLOR OR B/W        -   IMAGE MODE—TEXT, TEXT/PHOTO, PHOTO; EXPOSURE LEVEL        -   RESOLUTION        -   FILE FORMAT—FILE TYPE, COMPRESSION, AND PAGES PER FILE        -   ORIGINAL—ORIGINAL SIZE, SIMPLEX/DUPLEX, ROTATE, AND JOB            BUILD        -   FILENAME        -   SUBJECT        -   MESSAGE        -   SENDER        -   SCHEDULE SEND TIME        -   PAGE DIVISION (BOOK SCANNING)        -   COVER PAGE        -   TRANSMISSION MESSAGE (CONFIDENTIAL, URGENT, ETC.)        -   THIN PAPER SCANNING        -   DESTINATION        -   DOCUMENT FILING    -   Initiate Scan—the remote computing device application can        initiate the scan function (same as user pressing start button).

In some embodiments, a remote computing device can change the defaultvalues on the imaging device or the values for the current job. For thecurrent job, the remote computing device may also specify if scanparameters may be modified by the user or not. If one remote computingdevice application (e.g. Access Control) specifies that a parametercannot be changed and then a second application (e.g. DocumentManagement) tries to set the parameter, a notification may be sent tothe second application and the setting will not be changed.

Print API

In some embodiments, print jobs may be submitted by remote computingdevice applications using standard printing channels. In some exemplaryembodiments, a Print API may provide a remote computing device with thefollowing additional control:

-   -   PJL sniffing—an RCD application can register with the IDev to be        contacted for instructions when a specific PJL command is found        in a print job. The RCD can then instruct the IDev to replace        the command, cancel the job, or continue printing. This        interface may be used in applications like accounting and        other-brand compatibility.        Copy API

In some embodiments of the present invention, a Copy API may provide aremote computing device with the following exemplary controls:

-   -   Copy Parameters—an RCD application can get and set values for        the following copy parameters:        -   COLOR OR B/W        -   EXPOSURE—TEXT, TEXT/PHOTO, PHOTO, SUPER PHOTO; EXPOSURE            LEVEL        -   PAPER SELECT (BY TRAY)        -   COPY RATIO        -   2-SIDED COPY—1TO1, 1TO2, 2TO2, 2TO1; BINDING EDGE        -   OUTPUT—OUTPUT TRAY, SORT, STAPLE, GROUP, OFFSET        -   ORIGINAL SIZE        -   SPECIAL FUNCTIONS—MARGIN SHIFT, ERASE, PAMPHLET, ETC.        -   DOCUMENT FILING    -   Initiate Copy—an RCD application can initiate the copy function        (same as user pressing start button).

In some embodiments, a remote computing device can change the defaultvalues on the imaging device or the values for the current job. For thecurrent job, the remote computing device may also specify if copyparameters may be modified by the user or not.

Document Filing API

In some embodiments of the present invention, a Document Filing API mayprovide a remote computing device with the following exemplary controls:

-   -   Backup/restore—the remote computing device application can        import and export a batch file with all Document Filing data. In        some embodiments, this package will be in a proprietary format        since it contains documents that are password-protected and        should not be accessed individually—this is typically for        restore in case of failure or cloning to other devices.    -   File/folder list—the remote computing device application can        retrieve, modify, and create new files and folders to be stored        on the IDev (also covered in device management).    -   Download file—the remote computing device can download a new        file to the Document Filing systems and specify folder,        filename, username, and password.    -   User list—the remote computing device application can retrieve,        modify, and create new users to be stored on the IDev (also        covered in device management).    -   HDD Status—the remote computing device application can retrieve        the current HDD status including the % allocated to the main        folder, quick folder, and custom folders and the % remaining.    -   Doc Filing Parameters—the remote computing device application        can get and set values for storing a file to Doc Filing        including:        -   EXPOSURE        -   RESOLUTION        -   ORIGINAL—SIZE, SIMPLEX/DUPLEX        -   FILE INFORMATION—USERNAME, FILENAME, FOLDER, CONFIDENTIAL,            PASSWORD        -   SPECIAL MODES—ERASE, DUAL PAGE COPY, 2IN1, JOB BUILD, CARD            SHOT    -   Initiate Print—the remote computing device application can        select a stored file and initiate a print including the        following parameters:        -   PAPER SIZE/SOURCE        -   OUTPUT—SORT/GROUP, OUTPUT TRAY, STAPLE, PUNCH, OFFSET        -   SIMPLEX/DUPLEX (TABLET/BOOKLET)        -   TANDEM PRINT        -   NUMBER OF COPIES        -   DELETE OR STORE AFTER PRINTING    -   Initiate Send—the remote computing device application can select        a stored file and initiate a send including the following        parameters:        -   RESOLUTION        -   FILE FORMAT        -   DESTINATION        -   TIMER        -   SENDER        -   FILENAME        -   SUBJECT        -   MESSAGE

Security

Allowing external applications to control an imaging device opens up theimaging device to new security vulnerabilities. In embodiments of thepresent invention that provide some security measures, the followingexemplary items are security concerns that may be addressed by theremote computing device interface.

Access to remote computing device interfaces may be limited to validapplications. Embodiments provide extensive access and control of theimaging device, which poses a significant security risk. The interfaceof these embodiments may be protected from access by attackers, whilemaintaining ease of setup and use for valid solutions.

Confidential data (user credentials and job data) may be protectedduring network transfer. User credentials and job data may be securedduring network transfer to ensure that it cannot be stolen, an intrudercannot monitor device activity, and a man-in-the-middle attack cannotchange messages. Imaging devices may support Secure Sockets Layer (SSL)and other connections to ensure data is safe while being communicatedbetween the imaging device and remote computing device applications.

Administrators may have the ability to lock-down imaging device access.For users with strict security policies, administrators may have theability to disable access by remote computing devices or limit access tospecific applications. Administrators may have an option to register thelimited applications that they wish to access the imaging deviceinterfaces.

Remote computing device applications may ensure the imaging device isnot being “spoofed.” The remote computing device may be able toauthenticate an imaging device that it is contract with it to ensure anintruder cannot imitate the imaging device to collect networkconfiguration and password information, monitor file/folder structuresof a document management system, or spoof security settings and DSKstatus of the imaging device.

A remote computing device may ensure that the server is not being“spoofed.” The imaging device must be able to authenticate all remotecomputing devices that it is in contact with to ensure that an intruderis not spoofing the remote computing device's IP address. By pretendingto be the remote computing device, an intruder could steal usercredentials, redirect scanned documents, change device settings orfirmware, or bring down the access control system (either to provideaccess to unauthorized users or initiate a denial of service attack forvalid users).

Access control/vend applications may not be compromised when a remotecomputing device is unavailable. When the remote computing device isunavailable, it may not be acceptable to provide open access to thedevice. If the remote computing device is unavailable at startup orbecomes unavailable at anytime (e.g. someone disconnects network cable),the imaging device may immediately be disabled and an error messagedisplayed.

An administrator may be able to adjust a security level based on companyand application requirements. Security requirements can have a largeimpact on the time it takes to develop a remote computing deviceapplication and the resources required to implement the solution. Usersusing some embodiments may range from a small business with one imagingdevice, no IT staff, and a simple scan or print application to a largegovernment office using access control and audit trails to track alldevice activity. The security measures used to protect imaging deviceinterfaces may be adjustable by the administrator to match the targetenvironment.

The imaging device and remote computing device applications may be ableto hand-off user credentials. Users may be prompted to login at multiplepoints throughout a job. For example, an access control application oraccounting application may control total device access, the imagingdevice may have user authentication enabled for Image Send, and adocument management application may require user login before showing afolder list. In many environments, all of these applications will use acommon user database. In some embodiments, it is, therefore, desirablefor the applications to pass user credentials to each other, so thateach one does not have to repeat the authentication process.

Some embodiments of the present invention may be described withreference to FIG. 3. These embodiments comprise an imaging device only,which is configured to interact with a remote computing device, such asa server through a communications link. The imaging device 30 comprisesa user interface 32, which comprises a user input device 34, such as akeypad, one or more buttons, knobs or switches or a touch-screen paneland a display 36, which may comprise user input device 34 in the form ofa touch-screen panel.

Imaging device 30 will typically be capable of performing one or moreimaging functions including, but not limited to, scanning, printing,copying, facsimile transmission (sending and receiving) and others.

These embodiments further comprise a communications link 38, which maybe a wired connection (as shown in FIG. 3) comprising a network cable, aUniversal Serial Bus (USB) cable, a serial cable, a parallel cable, apowerline communication connection such as a HomePlug connection orother wired connections. Alternatively, the communications link 38 maycomprise a wireless connection, such as an IEEE 802.11(b) compliantconnection, a Bluetooth connection, an Infrared Data Association (IrDA)connection or some other wireless connection.

The operation of some imaging device embodiments may be explained withreference to FIG. 4. In these embodiments, menu data is received 40 froma remote computing device (not shown in FIG. 3), which is connected tothe imaging device 30 via the communication link 38 through a wired orwireless connection. This menu data is then displayed 42 on the imagingdevice user interface display 36. This display of remote menu data isintended to prompt a user to make an input on the user interface inputdevice 34.

Imaging devices of these embodiments are further configured to acceptinput from a user in response to a display of remote menu data andcommunicate 44 that user input to a remote computing device. In someembodiments, this user input data will be processed by a remotecomputing device. This may comprise running an application on the remotecomputing device. This processing may also comprise accessing andcommunicating data that is stored on the remote computing device.

The imaging devices of these embodiments are further configured toreceive 46 data resulting from processing the user input data. This maycomprise data generated by an application running on the remotecomputing device in response to the user input. The imaging device mayalso receive data that was stored on a remote computing device, such asa file server, in response to processing the user input.

Once the imaging device 30 has received 46 the processed data, theimaging device 30 may perform 48 a native function in response to thedata or using the data. For example, and not be way of limitation, theimaging device 30 may print a document that was stored on the remotecomputing device and modified on the remote computing device accordingto the user input. As another non-limiting example, the imaging device30 may active or enable functions (i.e., scanning, copying, printing,fax transmission) on the imaging device in response to the receipt 46 ofprocessed data.

Some, more specific, imaging device embodiments may be explained withreference to FIG. 5. In these embodiments, the imaging device 30 isconfigured to receive 50 menu data formatted in a markup language from aremote computing device. The communication link by which the menu datais communicated may be established and maintained using a HypertextTransfer Protocol (HTTP). The markup language may comprise terms fromHypertext Markup Language (HTML), Extensible Markup Language (XML),Wireless Markup Language (WML), Extensible Hypertext Markup Language(XHTML) and/or other languages.

Once the menu data is received 50, it may be displayed 52 on the imagingdevice user interface display 36. As in previously describedembodiments, the menu data is typically intended to prompt user input onimaging device user interface 32. Display 52 of the remotely-stored menudata may be accomplished with a browser application that is native tothe imaging device 30.

In these embodiments, the imaging device 30 is further configured toroute 54 user input received though its user interface 32 to a remotecomputing device. The remote computing device that receives the userinput may then run an application or otherwise process the user inputand return the results of the processing to the imaging device 30.Accordingly, the imaging device 30 is further configured to receive 56processed data from a remote computing device. In some embodiments, theimaging device 30 may perform one or more functions in response to thereceipt 56 of processed data.

Some embodiments of the present invention may be explained withreference to FIG. 6. These embodiment comprise a remote computing device(RCD) 60, which has a communications link 64. Communications link 64 maybe a wired connection (as shown in FIG. 6) comprising a network cable, aUniversal Serial Bus (USB) cable, a serial cable, a parallel cable, apowerline communication connection such as a HomePlug connection orother wired connections. Alternatively, the communications link 64 maycomprise a wireless connection, such as an IEEE 802.11(b) compliantconnection, a Bluetooth connection, an Infrared connection, such asthose defined in the Infrared Data Association (IrDA) standard or someother wireless connection. In some embodiments, RCD 60 may furthercomprise a data storage device 62, which is typically a hard drive, butmay also be an optical drive device, such as an array of compact diskdrives, flash memory or some other storage device.

Embodiments of RCD 60 may be further described with reference to FIG. 7.In these embodiments, RCD 60 comprises a processor 72 for processingdata and running programs such as operating systems and applications.RCD 60 may further comprise memory 74, which may be in the form ofRandom Access Memory (RAM) and Read Only Memory (ROM). Generally, anyapplications processed by processor 72 will be loaded into memory 74.RCD 60 may further comprise a network interface 78, which allows RCD 60to communicate with other devices, such as an imaging device 30. In someembodiments, RCD 60 may also comprise a user interface 80, but this isnot required in many embodiments. Storage 62 may be used to storeapplications and data that may be accessed by an imaging device 30 ofembodiments of the present invention. Processor 72, memory 74, storage62, network interface 78 and, optionally, user interface 80 aretypically linked by a system bus 76 to enable data transfer between eachcomponent. Communications link 64 may couple the RCD 60 to other devicesvia network interface 78.

In some embodiments, described with reference to FIG. 8, an RCD 60 maycomprise menu data stored on storage device 62 or in memory 74. Thismenu data may be configured for display on an imaging device userinterface 32. Menu data may be stored in many formats andconfigurations. In some embodiments menu data may take the form of termsexpressed with a markup language. The markup language may comprise termsfrom Hypertext Markup Language (HTML), Extensible Markup Language (XML),Wireless Markup Language (WML), Extensible Hypertext Markup Language(XHTML) and/or other languages. In these embodiments, menu data may besent 82 through a communications link 64 to an imaging device 30.Accordingly, menu data configured for display on an imaging device isstored on RCD 60.

An RCD 60, of some embodiments, will be further configured to receive 84user input obtained through the user interface 32 of an imaging device30 and transferred to the RCD 60 over communications links 38 & 64. Oncethis input data is received at an RCD 60, the input data may beprocessed 86. This processing 86 may comprise conversion of the data toa new format, execution of commands contained within the data or someother process. Once the input data has been processed 86, the processedoutput may be sent 88 back to the imaging device 30 where the processedoutput may be used in an imaging device process or function.

In some embodiments, as described with reference to FIG. 9, an RCD 60may send 90 menu data configured for an imaging device display 36 usinga markup language. The markup language menu data is then received at theimaging device 30 and displayed to a user. Typically, this will promptthe user to enter an input on the imaging device user interface 32. Thisuser input will then be sent by the imaging device 30 to the RCD 60. TheRCD 60 will then receive 92 the input data prompted by the display ofthe menu data on the imaging device 30. Once received, the input datamay be processed 94 on the RCD 60. Processing may comprise theselection, recordation and/or modification of a form, document or otherdata stored on RCD 60, the authorization of a user identified by theuser input, the translation of a document input by the user, generationof a map or other directions related to user input or some other processor function.

Some embodiments of the present invention may be described withreference to FIGS. 10 & 11. These embodiments comprise at least one RCD60 and a plurality of imaging devices 30 a-30 d. In these embodiments,at least one of the imaging devices 30 a-30 d comprises a user interface32 with a display 36 and user input panel 34 that is integral with thedisplay (i.e., touch-screen) or a separate input unit. RCD 60 isconnected to imaging devices 30 a-30 d by a communications link andnetwork 100 to enable data transmission between RCD 60 and imagingdevices 30 a-30 d.

In these embodiments, menu data is stored on RCD 60 and sent 110 to atleast one of the imaging devices 30 a-30 d where the menu data isdisplayed on a user interface. Any of Imaging devices 30 a-30 d thatreceive the menu data are configured to accept 112 and transmit 114 userinput to an RCD 60. Once the user input data is received at the RCD, thedata may be processed 116 as discussed in previously describedembodiments. The result of processing 116 may then be sent 118 back toany combination of the imaging devices 30 a-30 d.

In these embodiments, a single RCD 60 may be used to provide processingpower, resources and functionality to a plurality of imaging devices 30a-30 d without reproducing these resources in each imaging device. Insome embodiments, data generated by input on one imaging device 30 a maybe directed to another imaging device 30 d for processed data output orfinal processing.

Some embodiments of the present invention may comprise multi-languagemenu support. Some of these embodiments, illustrated in FIG. 11B, allowfor an initial selection or identification 101 of a user-preferredlanguage. This selection may comprise user input to select a preferredlanguage. This step may also comprise an automatic identification of auser-preferred language which may be achieved by a user identificationprofile linked to a language, a language identification based on thetext of a scanned document, a code printed on a scanned document or someother identification scheme.

Once the language has been selected or otherwise identified, theselection/identification data is sent 102 to an RCD, where the selectionis used to identify language-specific menu data that is sent 103 to theimaging device for display 104. A user may then respond to theselected-language menu data with input 105, which may be used to invokenative imaging device functions or may be sent 106 to the RCD for anynecessary processing. An RCD may then process 107 the input data andsend 108 any process input to a destination, such as the imaging device,an e-mail address, a memory location or some other destination.

Dynamic Forms

Some embodiments of the present invention may be described withreference to FIG. 12. In these embodiments, an imaging device (IDev) 120comprises a user interface 124, which is capable of receiving user inputand displaying data to a user. The user interface 124 will typicallycomprise a display, often in the form of a touch panel. The display maybe used to display data 122 to a user. This data may comprise menu datato prompt for a user selection or data entry, such as a user ID andpassword, form selection or some other input. The imaging device 120 hasa communication link 126, which may comprise a typical computer networkconnection, a serial cable or some other wired or wireless communicationlink as described in other embodiments. The communication link 126connects the imaging device 120 to a remote computing device (RCD) 128,such as a server. The RCD 128 may be used to store documents, such asforms, and other data and make that data accessible from the imagingdevice 120. The RCD 128 may also execute applications that interact withor receive input from the imaging device 120 and its user interface 124.

The terms “modify” and “modification,” as used in this specification inrelation to documents, comprise the actions of document generation,document merging functions, document field assignments, search andreplace functions, and any other actions that cause a humanlyperceptible or machine perceptible change to a document.

The term “document content” or “content,” as used in this specification,comprises text, graphics, images, symbols and other data that isintended to be communicated by the document.

The term “user input” or “input,” as used in this specification,comprises input of content and instructions for an imaging device, aremote computing device or some other device. Input may be accomplishedby keypad entry, touch-screen entry, upload from another device or byother methods.

In some embodiments of the present invention, as illustrated in FIG. 13,user data is input on the user interface 124 of an imaging device 120.This user data is then sent 132 over a communication link 126 to an RCD128. When the data is received at the RCD, the RCD may apply 134 thedata to a document. This process may comprise modification 134 of thedocument, such as filling in the fields of a form, selecting optionalportions of a document, addressing a document, formatting a document andother modification procedures. The application 134 of data to a documentmay also comprise generation of a new document with the user data. Thismay be performed by an application running on the RCD 128. Once thedocument has been modified or generated, the document may be sent 138directly from the RCD 128 to a destination, such as an e-mail address, afax number, a network location or some other destination. The modifiedor newly generated document may also be sent 136 to the imaging device120 for output in some format, such as printed media, fax transmission,e-mail or some other format.

Some embodiments of the present invention are tailored for usercharacteristic data. These embodiments are illustrated in FIG. 14. Inthese embodiments, a user identifies 140 specific user characteristicdata by input on an imaging device user interface 124. This usercharacteristic data may comprise a user identification, a user location,a user occupation, a user marital status, a user gender, a user accountidentifier or some other user characteristics. This user characteristicdata is then sent 142 over a communication link 126 to an RCD 128. Whenthe data is received at the RCD 128, the RCD 128 may modify 144 adocument using the data. This process may comprise modification 144 ofan existing document, such as filling in the fields of a form, selectingoptional portions of a document, addressing a document, formatting adocument and other modification procedures. The modification 144 of adocument with user characteristic data may also comprise generation of anew document with the user characteristic data. As in other embodiments,this may be performed by an application running on the RCD 128. Once thedocument has been modified or generated, the document may be sent 148directly from the RCD 128 to a destination, such as an e-mail address, afax number, a network location or some other destination. The modifiedor newly generated document may also be sent 146 to the imaging device120 for output in some format, such as printed media, fax transmission,e-mail or some other format.

Further embodiments of the present invention, illustrated in FIG. 15,also comprise a document selection process. In these embodiments, a usermay input 150 user characteristic data or some other data at an imagingdevice user interface 124, as in other embodiments. This user input datamay be optionally sent 151 to an RCD before further input. In theseembodiments, a user may further select 152 a document from the imagingdevice user interface 124. This document selection 152 and any priorinput may then be sent 153 to an RCD 128 for processing. These userinput steps 150, 152 may be performed in several input steps throughmenu selections on the imaging device user interface 124. Each step maycomprise receiving input, sending the input to the RCD 128 andrefreshing the user interface display 124 for subsequent input steps.Menu data may be supplied from the imaging device 120 or from the RCD128. When all required data has been input and sent to the RCD 128, theRCD 128 may modify 154 the selected document using the user input. Afterdocument modification or generation 154, the document may be sent to adestination 158 from the RCD or to the imaging device 120 for furtheroutput 156.

Some embodiments of the present invention comprise database access.These embodiments, illustrated in FIG. 16, allow user input data receipt160 at an imaging device user interface 124. Document selection input162 is also allowed at the user interface 124. This user input istransmitted 163 to an RCD 128, as in previously described embodiments.However, this user input is used to identify stored database data thatcan be accessed 164 for use in document modification. Once the userinput data and the supplemental database data is accessed by the RCD128, the data can be used to modify or generate 166 a document. Thedocument may then be sent to a destination 168 or to the imaging device169.

Further embodiments of the present invention may be described withreference to FIG. 17. These embodiments comprise a user query process.In these embodiments, a user selects 170 a document at an imaging deviceuser interface 124. This selection is then sent 171 to an RCD 128. TheRCD 128 may then determine what information is required to complete thedocument and query 172 the user for that specific information throughthe imaging device user interface 124. Input is then received 173 on theuser interface 124 and sent 174 to the RCD 128. The selected document isthen modified or generated 175 as previously described. Once modified orgenerated, the document may be sent to a destination 176 or to theimaging device 177 for output or further processing.

In still more embodiments of the present invention, as illustrated inFIG. 18, a document may be displayed 180 on an imaging device userinterface 124. This display 180 may be initiated by user selection, someautomated process or by some other selective method. In conjunction withthe document display 180, a user may be prompted to input data fordocument modification, such as filling out a form. User input is thenaccepted 181 at the user interface 124. This input data is then sent 182to an RCD 128 and the document that was displayed may be modified 183according to the user input received from the user interface 124. As inother embodiments, the modified document may be sent directly to adestination 184 or to the imaging device 120 for output or furtherprocessing 185.

Some embodiments of the present invention, illustrated in FIG. 19,utilize a markup language, such as an Extensible Markup Language (XML)and a message protocol such as Simple Object Access Protocol (SOAP). Insome exemplary embodiments, a user input is accepted 190 at an imagingdevice user interface 124. The input data is formatted 191 at theimaging device into a SOAP message using XML. The XML/SOAP message isthen sent to an RCD 128 over a communication link 126. The RCD 128 mayprocess 193 the XML/SOAP message entirely or partially and send parts ofthe message to other units on a network for processing. Processing ofthe message may require retrieval 194 of data stored on the RCD 128,another network storage device or from some other location. Once allrequired data has been retrieved, the data may be formatted 195 into adocument, such as a print job or e-mail, and sent 196 to a destinationor imaging device 120.

Some embodiments of the present invention, as illustrated in FIG. 20,comprise menu data that is stored on an RCD 128, but displayed on animaging device user interface 124. In some of these embodiments, menudata is sent 200 from an RCD 128 to an imaging device 120. This menudata is then displayed 201 on the imaging device user interface 124.User input, in response to the menu display, is accepted 202 at theimaging device user interface 124 and sent 203 to the RCD 128 forprocessing. This input data is then used at the RCD 128 to select ormodify 204 a document that is accessible to the RCD 128. Once thedocument has been modified, selected or generated, the finalizeddocument is sent 205 to a destination or to an imaging device 120 forfurther processing or output.

An RCD 128 comprising remote menu data for display on an imaging device120 may follow a method illustrated in FIG. 21. In these embodiments,the RCD 128 may send 210 menu data to an imaging device 120 for display.The display process will typically prompt for user input and relay thatinput back to the RCD 128, which will receive 212 the input data. Thisdata will then be used to complete, generate, format or otherwise modify214 a document, which will then be sent 216 to a destination or to animaging device 120 for further processing or output.

An imaging device 120 that receives remote menu data may follow a methodillustrated in FIG. 22. In these embodiments, the imaging device 120 mayreceive 220 menu data from an RCD 128. This menu data will be displayed222 on the imaging device user interface 124. This is typically done ina manner that prompts a user for input on the user interface 124. Inputis then accepted 224 on the user interface 124 and sent 226 to an RCD128 for processing. The RCD 128 then modifies a document in response tothe user input and sends the modified document to the imaging device120. The imaging device 120 receives 228 the modified document and sendit to a destination or converts it to hard copy output.

Further embodiments of the present invention comprising remote menu datamay be explained with reference to FIG. 23. These embodiments comprisedatabase or network resource access in conjunction with remote menudata. In some of these embodiments, menu data stored on an RCD 128 issent 230 to an imaging device 120 for display. The menu data isdisplayed 231 on the imaging device where input is prompted. User inputis accepted 232 at the imaging device user interface 124 and sent 233 tothe RCD 128 for processing. Processing on the RCD 128 may call forsupplemental data identified during processing. When this is the case,the RCD 128 may access 234 a database or other network resource toobtain the supplemental data. Once all necessary data has been obtained,the RCD 128 may modify 235 a document with the data and send 236 thatmodified document to the imaging device 120 for further processing oroutput.

An RCD 128 that utilizes remote menu display and data access may followthe steps illustrated in FIG. 24. In these embodiments, menu data may besent 240 to an imaging device 120 for display on a user interface 124.Data received from the imaging device 120 is received 242 at the RCD128. Any supplemental data called for in processing the user input datamay be accessed 244 from a database or other network or local resource.The input data and supplemental data may then be used to modify 246 adocument, which will then be sent 248 to the imaging device 120 forfurther processing or output.

An imaging device that utilizes remote menu data and remote data accessmay follow the steps illustrated in FIG. 25. In these embodiments,imaging device menu data is received 250 from an RCD 128 and displayed252 on the imaging device user interface 124. User input is accepted 254in response to the display of menu data and sent 256 to the RCD 128 forprocessing. After remote data access and document modification performedby the RCD, a modified document is received 258 at the imaging device120 from the RCD 128 and the modified document is output 259 by theimaging device 120.

Some embodiments of the present invention may operate without the aid ofa remote computing device that processes data and/or instructions. Someembodiments, illustrated in FIG. 26, comprise an imaging device (IDev)that does not require a communication link to other devices. The imagingdevice of these embodiments comprises a user interface with an inputdevice and a display. In these embodiments, document content may bereceived 260 on the IDev user interface. Other information, such as menuselections, formatting data and other user input may also be received atthe user interface. This document content may be used to add to orotherwise modify 262 a document that has been stored on the IDev. SomeIDevs of these embodiments comprise data storage capabilities for thestorage of forms, documents and other data. In some embodiments, adocument may be created from the document content input by the user andno storage capability is required. Once a document has been modified bythe user input content, the modified document may be sent 264 to adestination within the imaging device, such as another module of thedevice, for further processing or transmission or the document may besent 264 to a destination outside the imaging device through acommunication link.

Further embodiments of the present invention, illustrated in FIG. 27,are similar to those explained with reference to FIG. 26. Theseembodiments receive 270 input of document content at an imaging deviceuser interface. This content is used to add to or modify 272 (includingcreation of) a document's content. Once the document has been modified,the document may be output 274 using one of the imaging device imagingfunctions, such as, but not limited to, printing on media, transmittingas e-mail, transmitting as a facsimile and other output formats.

Still other embodiments of the present invention provide for documentmodification (including creation) on the imaging device. Theseembodiments may modify a document on the imaging device, howeverdocuments are stored remotely. In these embodiments, a user may select280 a document using the IDev user interface. The user may also input282 document content using the IDev user interface. When a document isselected, the document is pulled 284 from remote storage such as anetwork server, a remote computing device or some other storage deviceor location. When the document is retrieved by the IDev, the IDev maymodify 286 the document using the input document content. Once thedocument is modified using the new content, the modified document may beoutput 288 at the imaging device or sent to another destination.

Embodiments of the present invention that provide for documentmodification on the imaging device may use one or more Java-basedapplications that run on the imaging device.

Some embodiments of the present invention may be explained withreference to FIG. 29. In these embodiments, a form fill application 296may run on a server 291 or some other type of computing device that islocal to or remote to an imaging device (IDev) 290, but which isconnected to the IDev 290 through a communication link 295. The formfill application may also be connected to a file system 292 and adatabase 293. The IDev 290 may receive user input through an IDev UI andtransmit that input to the form fill application 296. The communicationlink 295 may facilitate transmission of commands and data between theform fill application 296 and the IDev 290. This may be performed via aHyperText Transfer Protocol (HTTP) or by other data transmissionprotocols. A form fill application 296 may retrieve file and file folderdata from an Operating System (OS) or Document Management System (DMS)file system. A form fill application 296 may also retrieve data from adatabase 293. A database 293 may comprise information related to a useraccount, such as a database of vacation time for employees.

In some embodiments of the present invention, a user may log onto anIDev 290 by identifying a user name, password and/or other indicia. Thisuser data may be passed to the form fill application and used to relateto other information, such as information stored in a database 293. Anapplication, such as a form fill application, may push display contentto an IDev user interface (UI) that may invoke other elements of theapplication. An application may also be invoked by content that isresident on the IDev and linked to the application. In either case, anapplication may be invoked by user input at the IDev UI. The applicationmay then respond by sending further content to the IDev UI to enablefurther functionality. If a user has not yet signed in, a logon page maybe sent to the UI in response to an application selection. In someembodiment a series of application selections may be displayed on theIDev UI. If a form fill application is selected, the application maysend content to the IDev UI that allows a user to select from a set offorms that are available through the form fill application.

Some forms may be stored on a file system 292. A user may need tonavigate through the file system. In this case, the file systemorganization and structure may be sent to the IDev UI and displayed to auser for selection and navigation. For some embodiments, details of thisprocess may be explained in co-pending U.S. patent application Ser. No.11/192,615, incorporated herein by reference.

Once a form has been selected and a user has been identified, and, insome embodiments authenticated, the system may access a database 293 andobtain data related to the user that also corresponds to the selectedform. This data may be used to populate fields in the form. In anexemplary embodiment, a vacation or time off request form may beaccessed. The system may access a database 293 to determine the numberof days the user has already used up and the total number of vacationdays the user is allotted. The system may then calculate the number ofdays available to the user and populate the form with this informationas well.

Once the form has been populated with field data, it may be sent to adirect print utility (DPU) 294 or some other type of print process forpreparation and forwarding 295 to a printer, such as IDev 290.

In some embodiments, illustrated in FIGS. 30 & 31, a form may be created305 by known methods. The form may comprise one or more fields 306 thatmay be filled with data from another source. When a form is selected 300at the IDev UI, the form fill application may recall 302 data related tofields in the form. This recall may be performed with an HTTP request301. The application may then make 303 a copy 304 of the form and appendthe related field data to the form. In some embodiments, an AdobePostscript® file may be used and the field data may be appended to thePostscript form file.

Once the Postscript form file 304 with the appended field data has beencreated, the form fill application 312 may call a direct print utility(DPU) to print the form, as illustrated in FIG. 31. The application 312may call the DPU and pass the Postscript file 304 to the utility. Theutility may then send the file 304 to the IDev 290 for printing.

In some embodiments, a form may be automatically filled with field dataassociated with the currently logged-in user. In other embodiments, theother users may be selected. Field data may be appended to thePostscript file using XML tags. In these embodiments, the field datawill appear in the appropriate place in the printed form.

In other embodiments, a form may be selected by a user and the systemmay respond by prompting the user to input data corresponding to thefields in the form. User input may be appended to the form in a mannersimilar to that explained above and the form may be printed using a DPUor by other methods. When user input is received, the input may bevalidated.

Some embodiments of the present invention may be described withreference to FIG. 32. In these embodiments, an IDev UI may display formselection content 320 allowing a user to select one or more forms. Thiscontent may reside on the IDev or may be sent to the IDev from a remotesource. When a form is selected at the IDev UI, the selection istransmitted to a form fill application comprising one or more forms321A-321C with field variables. Each form may be associated with aninput field definition file (IFDF) 322A-322C that defines the formfields within the form. An IFDF 322A-322C may also comprise displayparameters and UI options for prompting a user for field input. An IFDF322A-322C may also comprise instructions for obtaining field data fromother sources, such as a database, memory or another source. The IFDF322A-322C may be a markup language file, such as an XML file.

IFDF data may be sent to the IDev UI for incorporation into a user inputprompt display 323 for prompting a user to input field data. IFDF datamay be sent to the IDev using a template system as described inco-pending U.S. patent application Ser. No. 11/233,270, which isincorporated herein by reference.

A user may respond to the input prompt 323 by selecting from anenumerated list, typing on a soft keyboard or hard keyboard or by otherknown methods. Once input has been entered, the entries may be sent topost-processing modules 324A-324C that correspond to the specific formsselected. A post-processing module 324A-324C may process the user inputdata and generate appropriate tags and tag values. In some embodiments,this data may be formatted into markup language tags. These formattedtags may then be appended to a form file that corresponds to the formselected by the user to create a filled-in form 325A-325C with fieldsthat are populated with user input.

Once a filled-in form 325A-325C has been created, the form 325A-325C maybe sent 326 to a DPU for printing or printed in some other manner. Theresult of the printing process will be a hard-copy filled-in form 327comprising fields that are populated with the user input received at theIDev UI or data received by other means.

Some embodiments of the present invention may be described withreference to FIGS. 33A and 33B. In these embodiments, a server-basedform fill application 360, which may be remote to the IDev, is invokedby user input at the IDev UI or by some other method. This input may beformatted as an HTTP request 331 from a page on the IDev UI display.When the form fill application 360 is invoked, the application mayrequest 337 a set of form files 335 from an OS file system 361 or someother document management or file system. In some embodiments, theseform files 335 may be in an Adobe Postscript® format.

The form fill application 360 may read form file information and format334 a response 338 in a markup language format, e.g., XHTML, which maycomprise a list of available form files. This response may then be sentto the IDev UI 333 as an HTTP response or via another mechanism. Thisresponse, when received at the IDev UI 333, may then be displayed as auser prompt 332, which prompts a user to select a form from among thedisplayed list. When a user makes a form selection, that selection maybe formatted as an HTTP request 359 designating the selected form. Theform fill application 360 may then retrieve 339 a corresponding fielddefinition file 336. The application 360 may then dynamically create 340a markup language page, e.g., XHTML, comprising form field information.This form field page may then be sent to the IDev UI 333 as an HTTPResponse 345. When received at the IDev UI 333, the form field page maybe displayed as a user field data entry prompt 342.

A user may respond to the field data entry prompt 342 by entering fielddata 346, which may be received at the IDev UI and formatted into anHTTP Request 347 comprising field data entries. The form fillapplication 360 may then make a copy 348 of the selected form 349 andappend 350 the field data thereby creating a completed form 351comprising the field data 352.

The application 360 may then call 353 a direct print utility (DPU)application to print the completed form. In some embodiments, the formwill be a Postscript file with appended XHTML field data, however, otherfile formats and markup languages may be used in various embodiments.The DPU may send 354 the print job to a printing device 356 forprinting. In some embodiments, the printing device 356 may be part ofthe IDev. In other embodiment, the printing device 356 may be a separatedevice from the IDev on which the input was received. After printing, ahard copy form 358 comprising printed field data received from the userwill be the result.

The terms and expressions which have been employed in the foregoingspecification are used therein as terms of description and not oflimitation, and there is no intention in the use of such terms andexpressions of excluding equivalence of the features shown and describedor portions thereof, it being recognized that the scope of the inventionis defined and limited only by the claims which follow.

1. A method for imaging device remote document modification, said methodcomprising: receiving form file menu content and imaging device (IDev)device instructions at a hardware IDev via an IDev device managementapplication programming interface (API), wherein said form file menucontent and said IDev device instructions are received from a remoteapplication; displaying said form file menu content on an IDev userinterface (UI) display, wherein said IDev UI display in an integral partof said IDev; associating an IDev UI input key on said IDev with saidform file menu content; receiving a user input selection from said UIinput key, said user input selection identifying a form file requestrelated to said form file menu content; sending said form file requestfrom said IDev device management API to said remote application;receiving display content at said IDev device management API from saidremote application, said display content comprising a list of availableforms; displaying said list of available forms on said IDev userinterface (UI) display; associating a second IDev UI input key on saidIDev UI with a form identified in said list of available forms;receiving a second user input selection from said second UI input key,said second user input selection identifying said form identified insaid list of available forms; sending said second user input selectionfrom said IDev device management API to said remote application;receiving an input field definition file (IFDF) associated with saidform identified by said second user input selection at said IDev devicemanagement API, wherein said IFDF is a markup language file thatcomprises display parameters, field input menu content for fields insaid form and UI options for prompting a user for field input and saidIFDF also comprises instructions for obtaining field data from othersources; prompting a user for field data user input at said IDev UI,said field data user input comprising field data, wherein said promptingcomprises using a display prompt configured with said IFDF, and whereinsaid prompting is effected by said IDev device management API; obtaininga field data entry in response to said display prompt at said IDev UI;sending said field data entry in response to said display prompt fromsaid IDev device management API to said remote application; receiving,at said IDev, a completed form, wherein said completed form isgenerated, at said remote application, by appending said field dataentry to a form file representing said form selection thereby creatingsaid completed form; and outputting said completed form as hard copyoutput at said IDev.
 2. A method as described in claim 1 furthercomprising requesting file data from a remote resource where form filesare stored using source data in said IFDF.
 3. A method as described inclaim 1, wherein said display content is formatted in a markup language.4. A method as described in claim 1 further comprising sending a useridentification to said remote application from said IDev for the purposeof filtering said list of available forms based on said useridentification.
 5. A method as described in claim 1, wherein said formfile is a printer-ready file and said field data entry is appended as amarkup language tag.
 6. A system for imaging device remote documentmodification, said system comprising: a hardware imaging device (IDev)comprising an IDev device management application programming interface(API) for receiving form file menu content and IDev device instructionsfrom remote applications, wherein said form file menu content and saidIDev device instructions are received from a remote application; an IDevuser interface (UI) comprising a UI display for displaying said formfile menu content, wherein said IDev UI display in an integral part ofsaid IDev; a first IDev UI input key on an IDev UI, a first input keyconfigurator for associating said first IDev UI input key with said formfile menu content such that a user input selection using said UI inputkey identifies a form file request related to said form file menucontent; a first sender for sending said form file request from saidIDev device management API to said remote application; wherein said IDevdevice management API receives display content from said remoteapplication in response to said sending, said display content comprisinga list of available forms; said IDev UI display for displaying said listof available forms; a second IDev UI input key on said IDev UI; a secondIDev UI input key configurator for associating said second IDev UI inputkey with a form identified in said list of available forms such that asecond user input selection from said second IDev UI input keyidentifies said form identified in said list of available forms; asecond sender for sending said second user input selection from saidIDev device management API to said remote application; wherein said IDevdevice management API receives an input field definition file (IFDF)associated with said form identified by said second user input selectionin response to said sending with said second sender, wherein said IFDFis a markup language file that comprises display parameters, field inputmenu content for fields in said form and UI options for prompting a userfor field input and said IFDF also comprises instructions for obtainingfield data from other sources; said IDev device management API and saidIDev UI display for prompting a user for field data user input, saidfield data user input comprising field data, wherein said promptingcomprises using a display prompt configured with said IFDF; said IDev UIfor obtaining a field data entry in response to said display prompt;said IDev device management API for sending said field data entry tosaid remote application; said IDev device management API for receiving acompleted form, wherein said completed form is generated, at said remoteapplication, by appending said field data entry to a form filerepresenting said form selection thereby creating said completed form;and a hard copy output device for outputting said completed form as hardcopy output at said IDev.
 7. A system as described in claim 6 whereinsaid IDev device management API requests file data from a remoteresource where form files are stored using source data in said IFDF. 8.A system as described in claim 6, wherein said display content isformatted in a markup language.
 9. A system as described in claim 6wherein said IDev device management API sends a user identification tosaid remote application for the purpose of filtering said list ofavailable forms based on said user identification.
 10. A system asdescribed in claim 6, wherein said form file is a printer-ready file andsaid field data entry is appended as a markup language tag.